Release 10.1A: OpenEdge Development:
Progress Dynamics Repository Reference

ryt_dbupdate_status table — rytds

This table audits what Progress Dynamics Conversion Utility (DCU) updates have occurred. It also controls the DCU update after completion of the DCU and allows it to be rerun or restarted as required.

To successfully run a conversion, the DCU must do several tasks. It must control and automate the tasks done for a specific release and the stage during which they should be run. It also needs to track whether each step completed successfully, the order of the steps, and other information.

Certain tasks can only occur after the DCU has finished. But they require a valid login to complete and must be finished before anybody starts using the system. Controlling this process is the main reason for this table. This table significantly improves the load-and-go functionality within Progress Dynamics and helps prevent migration and deployment issues.

The DCU uses the information in the .pfl file to update this table.

Table 3–23 lists the table’s FLA, fields, and foreign keys.

Table 3–23: ryt_dbupdate_status table information 

Table FLA	Fields (data type)	Foreign keys
rytds	dbupdate_status_obj (Decimal) update_db_name (Character) delta_version (Integer) file_type (Character) file_name (Character) update_when (Integer) run_sequence (Integer) update_completed (Logical) update_successful (Logical) return_result (Character) run_date (Date) run_time (Integer) run_by_user_obj (Decimal) update_new_db (Logical) update_existing_db (Logical) rerunnable (Logical) update_mandatory (Logical)	None

Table 3–24 gives details of the table’s indexes.

Table 3–24: ryt_dbupdate_status index information 

Index name	Elements	Type
XPKryt_dbupdate_status	dbupdate_status_obj	Primary Unique
XAK1ryt_dbupdate_status	update_db_name delta_version file_type file_name update_when	Unique
XIE1ryt_dbupdate_status	update_completed update_when run_sequence	Nonunique
XIE2ryt_dbupdate_status	run_by_user_obj	Nonunique